I have written tests in my other apps that work fine w/ Suspense. I think this is related to findComponent.

We should support this. findComponent needs to work 100% of the time in all scenarios to be supported. If we can't accomplish this, then we should not include it. Alternatively, we throughly document what it can do and the associated restrictions. I will play around with this now.

@dobromir-hristov may have some ideas, he knows more about how findComponent works than I do.

Edit: looks Suspense does not have child components in the same way that a regular VNode does. Hm.

Edit edit: the blow by blow commentary continues - children in a Suspense are not an array, but a key:value pair:

{
      default: [Function: renderFnWithContext],
      fallback: [Function: renderFnWithContext],
      _: 1
}

This should be fixable. I tried turning these guys into an array but that did not work. I also tried doing findComponent({ name: 'Async' }) and adding a name: 'Async' but this also did not work.

I am worried what other edges cases are involved here, though. Excellent work catching this early. I definitely recommend asserting against the DOM where possible, as opposed to components.

As a quick sanity check, I added a test for <Teleport /> and it worked.

Done. Suspense is pretty much still Alpha and not complete.

wow, nice @dobromir-hristov. I tried something like that but it did not work 🤔

Great!

Actually @dobromir-hristov close, but not quite there.

I changed the test:

    const wrapper = mount(SuspenseComponent)
    expect(wrapper.findComponent(AsyncComponent).exists()).toBe(false)
    await nextTick()
    expect(wrapper.findComponent(AsyncComponent).exists()).toBe(true)

This is failing on the first assertion - because both default and fallback are in the Suspense tree. Any way to know which one is visible (other than the obvious solution of the DOM).

hm... Will check it out.

@dobromir-hristov @lmiller1990 Where are we on this PR?

I played with it but got nowhere... Will try again this week.

As this was bugging me, I read the code of vue-next and now understand better how suspense is implemented.
Based on your feedback, I opened #168 (I did not copy your Teleport test @lmiller1990 , feel free to open a PR to add it!) if you have time to review